docs: document the trigger skills installer (replaces agent rules)#3871
docs: document the trigger skills installer (replaces agent rules)#3871ericallam wants to merge 3 commits into
Conversation
WalkthroughThis PR rewrites and aligns documentation to introduce Trigger.dev agent skills installed via the bundled CLI command 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Rewrites the Skills page for the trigger skills command and the four bundled skills, turns the old Agent Rules page into a redirect to Skills, and collapses the Building with AI comparison to Skills vs MCP.
ericallam
force-pushed
the
docs/trigger-skills-command
branch
from
afa3b53 to
7b931f1
Compare
@trigger.dev/build
trigger.dev
@trigger.dev/core
@trigger.dev/plugins
@trigger.dev/python
@trigger.dev/react-hooks
@trigger.dev/redis-worker
@trigger.dev/rsc
@trigger.dev/schema-to-json
@trigger.dev/sdk
commit: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: cd90127b-559b-483a-987d-ccb9b78255a2
📒 Files selected for processing (4)
docs/building-with-ai.mdxdocs/mcp-agent-rules.mdxdocs/mcp-introduction.mdxdocs/skills.mdx
💤 Files with no reviewable changes (1)
- docs/mcp-introduction.mdx
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Build and publish previews
🧰 Additional context used
📓 Path-based instructions (1)
docs/**/*.mdx
📄 CodeRabbit inference engine (docs/CLAUDE.md)
docs/**/*.mdx: MDX documentation pages must include frontmatter with title (required), description (required), and sidebarTitle (optional) in YAML format
Use Mintlify components for structured content: , , , , , , /, /
Always import from@trigger.dev/sdkin code examples (never from@trigger.dev/sdk/v3)
Code examples must be complete and runnable where possible
Use language tags in code fences:typescript,bash,json
Files:
docs/mcp-agent-rules.mdxdocs/building-with-ai.mdxdocs/skills.mdx
🧠 Learnings (2)
📚 Learning: 2026-03-10T12:44:14.176Z
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3200
File: docs/config/config-file.mdx:353-368
Timestamp: 2026-03-10T12:44:14.176Z
Learning: In the trigger.dev repo, docs PRs are often companions to implementation PRs. When reviewing docs PRs (MDX files under docs/), check the PR description for any companion/related PR references and verify that the documented features exist in those companion PRs before flagging missing implementations. This ensures docs stay in sync with code changes across related PRs.
Applied to files:
docs/mcp-agent-rules.mdxdocs/building-with-ai.mdxdocs/skills.mdx
📚 Learning: 2026-04-30T20:30:29.458Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3226
File: docs/ai-chat/quick-start.mdx:13-13
Timestamp: 2026-04-30T20:30:29.458Z
Learning: In this repo’s documentation MDX files (`docs/**/*.mdx`), use `ts` and `tsx` (not `typescript`) as the code-fence language tags for TypeScript/TSX snippets. Do not flag `ts`/`tsx` code-fence language tags as incorrect in any docs MDX file, since this is the site-wide Mintlify-compatible convention.
Applied to files:
docs/mcp-agent-rules.mdxdocs/building-with-ai.mdxdocs/skills.mdx
🪛 LanguageTool
docs/building-with-ai.mdx
[uncategorized] ~43-~43: The official name of this software platform is spelled with a capital “H”.
Context: ...| .claude/skills/, .cursor/skills/, .github/skills/, .agents/skills/ | `mcp.json...
(GITHUB)
docs/skills.mdx
[uncategorized] ~27-~27: The official name of this software platform is spelled with a capital “H”.
Context: ... (.claude/skills/, .cursor/skills/, .github/skills/, .agents/skills/). It also w...
(GITHUB)
[uncategorized] ~64-~64: The official name of this software platform is spelled with a capital “H”.
Context: ...(https://github.com/features/copilot) | .github/skills/ | | [Codex CLI](https://github...
(GITHUB)
🔇 Additional comments (1)
docs/mcp-agent-rules.mdx (1)
1-41: LGTM!
| <Step title="Install Skills"> | ||
| Portable instruction sets that teach any AI coding assistant Trigger.dev best practices. Works with Claude Code, Cursor, Windsurf, VS Code (Copilot), and any tool that supports the [Agent Skills standard](https://agentskills.io). | ||
| Portable instruction sets that teach any AI coding assistant Trigger.dev best practices: writing tasks, realtime frontends, and `chat.agent` AI agents. They ship with the CLI, version-matched to your SDK, and install into Claude Code, Cursor, VS Code (Copilot), and Codex / AGENTS.md. | ||
|
|
||
| ```bash | ||
| npx skills add triggerdotdev/skills | ||
| npx trigger.dev@latest skills | ||
| ``` |
There was a problem hiding this comment.
Don't describe AGENTS.md as a skills install target.
Line 25 says skills install into “Codex / AGENTS.md”, but this page later correctly says the skills directory is .agents/skills/ and uses AGENTS.md only for the passive context-file fallback. That wording sends AGENTS-based users to the wrong place.
Suggested fix
- Portable instruction sets that teach any AI coding assistant Trigger.dev best practices: writing tasks, realtime frontends, and `chat.agent` AI agents. They ship with the CLI, version-matched to your SDK, and install into Claude Code, Cursor, VS Code (Copilot), and Codex / AGENTS.md.
+ Portable instruction sets that teach any AI coding assistant Trigger.dev best practices: writing tasks, realtime frontends, and `chat.agent` AI agents. They ship with the CLI, version-matched to your SDK, and install into Claude Code, Cursor, VS Code (Copilot), and AGENTS-compatible tools such as Codex via `.agents/skills/`.| The skills ship inside the `trigger.dev` CLI, version-matched to the SDK you have installed. Run: | ||
|
|
||
| ```bash | ||
| npx skills add triggerdotdev/skills | ||
| npx trigger.dev@latest skills | ||
| ``` | ||
|
|
||
| <Note>`skills` is an open-source CLI by Vercel. Learn more at [skills.sh](https://skills.sh).</Note> | ||
| The CLI detects your installed AI tools, lets you pick which skills to install, and copies each one into that tool's native skills directory (`.claude/skills/`, `.cursor/skills/`, `.github/skills/`, `.agents/skills/`). It also writes a one-line pointer into your primary instructions file (`CLAUDE.md`, `.cursor/rules`, etc.) so your assistant always knows the skills are there and loads the right one on demand. | ||
|
|
||
| The result: your AI assistant understands Trigger.dev's specific patterns for exports, schema validation, error handling, retries, and more. | ||
|
|
||
| ## Available skills | ||
| When you run `trigger dev` for the first time, the CLI offers to install the skills for you. | ||
|
|
||
| Install all skills at once, or pick the ones relevant to your current work: | ||
| <Note> | ||
| Because the skills are bundled with the CLI, the guidance your assistant gets is pinned to the | ||
| Trigger.dev version you are actually building against, instead of always being the latest from the | ||
| internet. |
There was a problem hiding this comment.
Fix skills versioning wording to match the CLI pinning behavior
docs/skills.mdx currently claims the skills are “version-matched to the SDK you have installed” / “pinned to the Trigger.dev version you are actually building against”, but the installer pins/stamps the bundled skills from the running/installing trigger.dev CLI version (the one you invoke with npx trigger.dev@latest skills), not from the project’s @trigger.dev/sdk version. Align this wording in docs/skills.mdx (lines 21-34 and 69-71) and update other pages that use the same “version-matched to your SDK” phrasing (e.g., docs/building-with-ai.mdx, docs/mcp-agent-rules.mdx).
Suggested wording direction
-The skills ship inside the `trigger.dev` CLI, version-matched to the SDK you have installed. Run:
+The skills ship inside the `trigger.dev` CLI. Run:
- Because the skills are bundled with the CLI, the guidance your assistant gets is pinned to the
- Trigger.dev version you are actually building against, instead of always being the latest from the
- internet.
+ Because the skills are bundled with the CLI, the guidance your assistant gets is pinned to the
+ CLI version you install. After you upgrade Trigger.dev, re-run the installer to refresh the
+ bundled skills.🧰 Tools
🪛 LanguageTool
[uncategorized] ~27-~27: The official name of this software platform is spelled with a capital “H”.
Context: ... (.claude/skills/, .cursor/skills/, .github/skills/, .agents/skills/). It also w...
(GITHUB)
1 participant
Summary
Updates the AI-tooling docs for the new
trigger skillsinstaller that shipped in #3868. The Skills page now documentstrigger skills(skills bundled with the CLI, version-matched to your SDK) and the four bundled skills:authoring-tasks,realtime-and-frontend,authoring-chat-agent,chat-agent-advanced. The old Agent Rules page becomes a short "rules are now skills" redirect (kept because existing redirects and the CLI link point at it), and the Building with AI overview collapses the three-way Skills/Rules/MCP comparison into Skills vs MCP.Hold until the v4.5 CLI release ships, since
trigger skillsis not on npm until then.